Onboarding EVM devs using SEO and GEO results#1377
Conversation
|
Nice 👍🏼 Will give it a review later today |
LUKSOAgent
left a comment
LUKSOAgent
left a comment
There was a problem hiding this comment.
Reviewed the PR locally.
corepack yarn install --immutable finished with existing peer warnings, and corepack yarn build completed successfully. Docusaurus still reports repo-wide broken-anchor warnings, but I did not see new broken route/relative-link failures from this EVM docs section.
I left one inline factual correction around LSP26 batching. Otherwise the structure is solid for the SEO/GEO onboarding goal.
| | Can another app read follows? | Only if it integrates that app | Yes, through standard functions | | ||
| | Is profile metadata standardized? | Usually separate | Yes, through Universal Profiles | | ||
| | Can profiles receive notifications? | App-specific | Yes, through LSP1 integration | | ||
| | Can follows be batched? | Depends on app | Yes, LSP26 supports batch functions | |
There was a problem hiding this comment.
This looks inaccurate against the current LSP26 docs. The standard page lists follow(address), unfollow(address), reads/counts, and events, but I don't see batch follow/unfollow functions exposed there. For an SEO entry page this should probably be changed to something like "Depends on the caller/app batching transactions" unless there is a concrete LSP26 batch API we can link to.
There was a problem hiding this comment.
the factual premise is wrong against the current standard docs. The live LUKSO LSP26 page lists followBatch(address[] memory addresses) and unfollowBatch(address[] memory addresses) under Core Functions, and the LSP-26 spec also includes both batch methods. So I would not change the claim to “depends on caller/app batching transactions”; that would be less accurate.
There was a problem hiding this comment.
3 participants
We’re adding an EVM-builder layer to the docs to improve SEO and GEO by answering the questions developers already search for or ask AI tools: ERC20 limitations, NFT metadata, receiver hooks, token discovery, smart-account permissions, gasless execution, and ERC1271 signatures. Instead of relying on builders to already know LUKSO terms like LSP7, LSP8, ERC725Y, or Universal Profiles, the new pages map familiar EVM problems to the LUKSO standards that solve them.
This helps LUKSO become more visible in organic search results and generative AI answers without changing the existing docs. The current documentation remains the technical source of truth, while the new section packages that depth into clearer, query-aligned pages that can rank, be cited, and guide builders from a known ERC problem into a practical LUKSO implementation path.
